Instead of using traditional HTTP status codes, errors are returned in the response alongside the data. These errors can be generated by the GraphQL server (for syntax or validation errors), as well as by resolvers (for business logic or runtime errors). Clients can then parse these errors and handle them accordingly, often using the error message and optional fields—like error codes or paths—to identify the nature and location of the error.